DTS Drop-Insert Mode

DTS supports deletion task processing in a mode known as drop-insert mode. The idea is to optimize the deletion task processing for tables with too many records relevant for deletion and not too many records in other clients. In short, the data is truncated on the database instead of the deletion of the individual DTS partitions.

Drop-insert mode should be used for tables with no primary index on the database. This is the case for some tables on S/4HANA or for SAP BW systems.

Drop-insert mode behaves differently for the read and the insertion task of each scenario. The description below is split per scenario and per transformation task:

• Conversion scenario:

  • Read task: The entire table, including data in other clients, is read and stored in the DTS cluster.

  • Deletion task: The table is dropped.

  • Insertion task: All records from the DTS cluster, i.e. also those from other clients, are inserted.

  NOTE This makes sense only for tables with a key field change. Other tables do not have a deletion task generated.

• Deletion scenario:

  • Read task: The negation of the selection, including data from other clients, is read and stored in the DTS cluster. Here, negation of the selection means everything that would not be selected if drop-insert mode were disabled.

  • Deletion task: The table is dropped.

  • Insertion task: The data read in the read task is inserted.

• Migration scenario: The SAP background job tables (TBT*) are processed differently.

  • Read task (executed on the source): Standard processing according to the scope setup.

  • Deletion task (executed on the target): Processing that differs based on the data in the other clients:

    • Table has data in other clients: The table is deleted via SQL DELETE statement.

    • Table does not have data in other clients: The table is dropped.

  • Insertion task (executed on the target): Standard processing according to the setup.

• Migration scenario TBT* tables: Only TBT* tables with the fields jobname and jobcount are processed this way.

  • Read task (executed on the source): The WHERE condition is predefined in the standard content. You can view the WHERE condition in the step Maintain table pool.

  • Deletion task (executed on the target): Records are deleted via SQL DELETE statement, but excluding any jobs scheduled or started by an SNP program.

  • Insertion task (executed on the target): Standard processing according to the setup.